Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tasks to build Docker build context artifacts #41819

Merged
merged 2 commits into from
May 7, 2019

Conversation

jasontedor
Copy link
Member

@jasontedor jasontedor commented May 4, 2019

This commit adds some tasks to generate dedicated Docker build context artifacts.

Closes #41454

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

This commit adds some tasks to generate dedicated Docker build context
artifacts.
@jasontedor jasontedor force-pushed the docker-build-context branch from 2ffbab4 to 210335e Compare May 4, 2019 20:21
@@ -0,0 +1,3 @@
apply plugin: 'base'

assemble.dependsOn ":distribution:docker:buildDockerBuildContext"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we adding new projects for thees ?
I'm not sure what value these bring.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@atorok It's the same structure as all of our other projects in distribution that produce artifacts, the only difference being there are explicit Gradle build files here instead of being wired up through Gradle magic in a root Gradle build file.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for the explanation!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason we have individual projects is so each of those projects has the one artifact as the default artifact. Here we aren't actually consuming this build context anywhere in tests that need to depend on one or the other right? In fact, we can likely get rid of the layers we have distribution now that we don't use dependency substitution anymore for them.

The thing that gives me pause most is having a hard dependency back to the :distribution:docker project on 2 tasks there. I don't see any benefit to running :distribution:docker:docker-build-context:assemble instead of :distribution:docker:buildDockerBuildContext

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rjernst I pushed a commit that I think addresses your concerns. The back dependency is gone.

Copy link
Contributor

@alpar-t alpar-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jasontedor jasontedor merged commit 30da73f into elastic:master May 7, 2019
jasontedor added a commit that referenced this pull request May 7, 2019
This commit adds some tasks to generate dedicated Docker build context
artifacts.
jasontedor added a commit that referenced this pull request May 7, 2019
This commit adds some tasks to generate dedicated Docker build context
artifacts.
jasontedor added a commit that referenced this pull request May 7, 2019
This commit adds some tasks to generate dedicated Docker build context
artifacts.
@jasontedor jasontedor deleted the docker-build-context branch May 7, 2019 01:13
jasontedor added a commit to jasontedor/elasticsearch that referenced this pull request May 7, 2019
* elastic/master: (414 commits)
  Add tasks to build Docker build context artifacts (elastic#41819)
  Replace more uses of immutable map builder (elastic#41823)
  Force selection of calendar or fixed intervals in date histo agg (elastic#33727)
  Switch run task to use real distro (elastic#41590)
  Clarify that path_match also considers object fields. (elastic#41658)
  [DOCS] remove 'es.scripting.update.ctx_in_params' system property for 7.0 (elastic#41643)
  Clarify _doc is a permanent part of certain document APIs. (elastic#41727)
  Remove the jdk directory to save space on bwc tests (elastic#41743)
  Fix full text queries test that start with now (elastic#41854)
  Remove `nonApplicationWrite` from `SSLDriver` (elastic#41829)
  SQL: [Docs] Add example for custom bucketing with CASE (elastic#41787)
  Cleanup Bulk Delete Exception Logging (elastic#41693)
  [DOCS] Rewrite `term` query docs for new format (elastic#41498)
  Mute PermissionsIT#testWhen[...]ByILMPolicy (elastic#41858)
  ReadOnlyEngine assertion fix (elastic#41842)
  [ML] addresses preview bug, and adds check to PUT (elastic#41803)
  Fix javadoc in WrapperQueryBuilder
  Testsclusters use seprate configurations per version (elastic#41504)
  Skip explain fetch sub phase when request holds only suggestions (elastic#41739)
  remove unused import
  ...
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
This commit adds some tasks to generate dedicated Docker build context
artifacts.
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team v6.8.0 v7.1.0 v7.2.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add task to produce Docker context artifacts
6 participants